Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEATURE: Workflow api now accepts an unnamed object or list of object… #2371

Conversation

urbanekv
Copy link
Contributor

@urbanekv urbanekv commented Jan 5, 2024

…s as a body json parameter. It could be mapped directly to a datastructure entity when a new field 'DatastructureEntityName' is set in the corresponding page parameter mapping.

…s as a body json parameter. It could be mapped directly to a datastructure entity when a new field 'DatastructureEntityName' is set in the corresponding page parameter mapping.
@urbanekv urbanekv marked this pull request as draft January 5, 2024 09:57
@urbanekv
Copy link
Contributor Author

urbanekv commented Jan 5, 2024

Documentation added: https://community.origam.com/t/parameter-mapping/2298

@urbanekv urbanekv marked this pull request as ready for review January 5, 2024 12:52
@origambot
Copy link

This pull request has been mentioned on ORIGAM Community. There might be relevant details there:

https://community.origam.com/t/make-workflow-page-api-to-accept-an-unnamed-object-or-a-list-of-objects/3271/2

@washibana washibana merged commit 7067af7 into master Jan 5, 2024
9 checks passed
@washibana washibana deleted the make-workflow-page-api-to-accept-an-unnamed-object-or-a-list-of-objects branch January 5, 2024 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants